In SAS^® Merchandise Allocation, there might be a performance degradation during the Batch Allocate process.  This issue is likely to occur when a Plan Like End date and Plan Like store are not in the DC Set. There are two different use cases from the Allocation Attributes Location tab in which a decrease in performance might occur:

1. A Plan Like store is outside the DC Set without a Plan Like End date.
2. A Plan Like store is inside or outside the DC Set with a Plan Like End date.

This decrease in performance is due to querying the database to capture the store data for every SKU being allocated.  This issue occurs when the apply merchandise/location attribute call is processed.

An example of each use case is as follows:

1. You allocate 25 SKUS and you have 1 Store defined to Plan Like a store not in your DC Set. The MAXDATA.MFINC table might be queried 25 times.
2. You allocate 25 SKUS and you have 1 Store that is defined to Plan Like a store that is or is not in your DC set but has a Plan Like End date. The MAXDATA.MFINC table might be queried 50 times (25 before the end date and 25 after the end date).

There is no workaround for this issue.

Operating System and Release Information